Business performance bookmarks

ABSTRACT

A performance bookmark of a dashboard view is created, e.g., in response to a triggering event. The performance bookmark includes a name, a timestamp, a reference to the visual properties of the dashboard view at the time that the performance bookmark is created and a reference to relationships of information displayed by the dashboard view at the time the performance bookmark is created. When a performance bookmark is recalled, the dashboard view is configured to correspond with the visual properties and relationships of information recorded at the time the select performance bookmark was created. Performance bookmarks are instances and relationships, and are not limited to snap shots captured of a static visual image of a dashboard screen from a corresponding dashboard user interface. As such, a retrieved dashboard view of a performance bookmark that is recalled from the bookmark system is live and supports user interaction.

BACKGROUND OF THE INVENTION

The present invention relates to systems, computer program products and computer methods for providing performance bookmarks that capture the state of business performance for advanced monitoring and analysis of business metrics.

A software “dashboard” is a tool that is used when managing a company's business performance by presenting role-based, content sensitive visibility of important business metrics in real time. Dashboard information can thus be utilized for monitoring and analyzing events in support of taking actions to improve and optimize a corresponding business. Examples of such metrics are the average response time of a supplier, the percentage of products failing quality control, the status of a particular order, the state of an insurance claim, the revenue stream of a retail product, the sales performance index for a particular geography, etc. Business metrics of particular business relevance are often called key performance indicators (KPIs).

Dashboards typically present a “live” view of the current state of the monitored events, e.g., by querying KPIs and then rendering the KPI data values through dashboard components such as gauges, tables and other visual metaphors. A dashboard is typically specific to a particular role within a business. Thus, the monitored events, and the visual display of those monitored events, may be configured in a manner appropriate to its corresponding role. For example, a vice president of insurance claims may determine a desired layout of a dashboard page, the collection of dashboard components to be used and the specific KPIs to be viewed in the components. A sales executive may have an entirely different dashboard layout, which considers a different collection of dashboard components and corresponding KPIs compared to the dashboard of the exemplary vice president of insurance claims. Regardless of the particular business role, dashboard layout or particular KPIs, as the data values of the KPIs change, the dashboard is immediately updated so as to provide a real time or near real time view of the state of the monitored events.

Typical dashboard applications address point in time issues by providing a specific dashboard component that shows the value of one or more KPIs along a time dimension. However, the time display of a given dashboard component does not capture the complete context of the entire dashboard, but rather reflects historical values for a single KPI.

BRIEF SUMMARY OF THE INVENTION

The present invention provides a computer implemented method, system and computer program product to bookmark a dashboard view. A performance bookmark of a dashboard view is created in response to a triggering event. The triggering event may comprise for example, an operator requesting that the performance bookmark be created, e.g., using a suitable interface of the dashboard view. The triggering event may alternatively comprise a system response, such as recognition of a predetermined action, e.g., detecting that an action has been taken as a result of an operator observation of the data within the dashboard view. The triggering event may alternatively comprise, for example, automatically detecting a threshold condition or other parameter related to a dashboard system, an automated process that triggers continuously, periodically or at some predetermined interval.

The performance bookmark includes attributes such as a name and a timestamp, a reference to the visual properties of the dashboard view at the time that the performance bookmark is created and a reference to relationships of information displayed by the dashboard view at the time the performance bookmark is created. The performance bookmark may also include other attributes such as a description, action and/or role/ID. An operator of the dashboard may also retrieve previously created performance bookmarks, wherein recalling a select performance bookmark configures the dashboard view to correspond with the visual properties and relationships of information recorded at the time the select performance bookmark was created.

Performance bookmarks are instances and relationships, and are not limited to snap shots captured of a static visual image of a dashboard screen from a corresponding dashboard user interface. As such, a retrieved dashboard view of a performance bookmark that is recalled from the bookmark system is live and supports user interaction.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

The following detailed description of various embodiments of the present invention can be best understood when read in conjunction with the following drawings, where like structure is indicated with like reference numerals, and in which:

FIG. 1 is a block diagram of a bookmark system according to an aspect of the present invention;

FIG. 2 is block diagram of a bookmark system according to an aspect of the present invention;

FIG. 3 illustrates a block diagram of a bookmark data structure that can be utilized with the bookmark system of FIGS. 1 and/or 2;

FIG. 4 is a chart illustrating exemplary alternatives for triggering the creation of a bookmark according to the various exemplary aspects of the present invention;

FIG. 5 is an illustrative screen display of a dashboard having a bookmark interface implemented as navigational bar at the bottom of the screen; and

FIG. 6 is an illustrative screen display of a dashboard having a bookmark, where an action event is recorded;

DETAILED DESCRIPTION OF THE INVENTION

The various aspects of the present invention may be embodied as a computer method, a system or computer program product. Also, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware, wherein the embodiment or aspects thereof may be generally referred to herein as a “circuit,” “module” or “system.” Furthermore, the present invention may take the form of a computer program product on a computer-usable storage medium having computer-usable program code embodied in the medium.

The software aspects of the present invention may be stored, implemented and/or distributed on any suitable computer usable or computer readable medium(s), including but not limited to, any medium that can contain, store, communicate, propagate or transport the program for use by or in connection with an instruction execution system of a corresponding processing device. The computer program product aspects of the present invention may have computer usable or computer readable program code portions thereof, which are stored together or distributed, either spatially or temporally across one or more devices. A computer-usable or computer-readable medium may comprise, for example, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium.

More specific examples of the computer usable or computer readable medium comprise for example, an electrical connection having one or more wires, a swappable intermediate storage medium such as floppy drive, tape drive, external hard drive, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a portable compact disc read-only memory (CD-ROM) or digital video disk (DVD), an optical fiber or storage device, or a transmission media such as those supporting the Internet or an intranet. The computer-usable or computer-readable medium may also comprise paper or another suitable medium upon which the program is printed, as the program can be electronically captured, for example, via optical scanning of the paper or other medium, then compiled, interpreted, or otherwise processed in a suitable manner, if necessary, and then stored in a computer memory.

In the context of this document, a computer-usable or computer-readable medium may be any medium that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. The computer-usable medium may include a propagated data signal with the computer-usable program code embodied therewith, either in baseband or as part of a carrier wave or a carrier signal. The computer usable program code may also be transmitted using any appropriate medium, including but not limited to the Internet, wireline, optical fiber cable, RF, etc.

Computer program code for carrying out operations of the present invention may be written in any suitable language, including for example, an object oriented programming language such as Java, Smalltalk, C++ or the like. The computer program code for carrying out operations of the present invention may also be written in conventional procedural programming languages, such as the “C” programming language, or in higher or lower level programming languages. The program code may execute entirely on a single computer, partly on one or more different computers, as a stand-alone software package, partly on a first computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the first computer through a network such as a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer, for example, through the Internet using an Internet Service Provider.

The present invention is described below with reference to flowchart illustrations and/or block diagrams of methods, apparatus systems and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams may be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

In the following detailed description of the illustrated embodiments, reference is made to the accompanying drawings that form a part hereof, and in which is shown by way of illustration, and not by way of limitation, specific embodiments in which the invention may be practiced. It is to be understood that other embodiments may be utilized and that changes may be made without departing from the spirit and scope of various embodiments of the present invention.

Referring now to the drawings and particularly to FIG. 1, a business performance monitoring and analysis system 10 is illustrated. The system 10 includes generally, a bookmark system 12, a dashboard system 14 and an operational environment 16. The bookmark system 12 allows an operator to save performance bookmarks, recall performance bookmarks and otherwise interact with performance bookmarks as will be described in greater detail herein. The dashboard system 14 is software that provides role-based, context-sensitive visibility of information, such as for the purpose of monitoring and/or analyzing business performance in support of actions that are directed to optimizing and/or improving the business or operations thereof. For example, the dashboard system 14 typically provides a workspace that allows real-time monitoring of visualizations, metrics and other visual metaphors that are organized into a window or windows that are periodically updated. The dashboard system 14 thus allows decision makers, such as management, consultants, executives, etc., to monitor their business processes, customer relationships, supplier relationships and other matters of business concern on an up to date basis. The operational environment 16 is a computer supported environment that maintains systems, which may include for example, applications, processes and data of interest to the system 10.

The bookmark system 12 comprises a bookmark management module 18, a bookmark data store 20 and a bookmark interface module 22. As used herein, a data store may comprise one or more databases, including relational databases, arrays, lists, or other structures that store data. The dashboard system 14 comprises an information management module 24, dashboard data stores 26, an application portal 28 and a dashboard user interface 30. The information management module 24 interacts with the operational environment 16 in order to obtain appropriate business information that is provided to the dashboard user interface 30. In one exemplary application, the information obtained from the operational environment 16 comprises performance information relating to predefined Key Performance Indicators (KPIs). As such, the information management module 24 is also referred to herein as a KPI management module 24.

The operational environment 16 may include, for example, a diverse number of processes, services software applications, databases, text, structured and unstructured documents, web pages, etc. For illustrative purposes, the operational environment 16 is shown as having customer relationship management software (CRM) 32, enterprise resource planning software (ERP) 34 and other miscellaneous process applications 36, which may include for example, workflow applications, office applications such as word processing, spreadsheet and database and presentation software.

The system 10 may be maintained on a single computer or the system 10 may be distributed across a network. Thus, the system 10 may be supported by networking components that interconnect the hardware and/or software processing devices, including for example, routers, hubs, firewalls, network interfaces wired or wireless communications links and corresponding interconnections. Moreover, the network may comprise connections using one or more intranets, extranets, local area networks (LAN), wide area networks (WAN), wireless networks (WIFI), the Internet, including the world wide web, and/or other arrangements for enabling communication between processing devices, in either real time or otherwise, e.g., via time shifting, batch processing, etc.

Moreover, the dashboard user interface 30 may be supported by any suitable processing device platform. Typical processing devices may include for example, servers, personal computers, notebook computers, transactional systems, appliance or pervasive computing devices such as a personal data assistant (PDA), palm computers, cellular access processing devices, special purpose computing devices and/or other devices capable of interacting with the system 10.

The data obtained by the information management module 24 from the operational environment 16 is transformed into information that may be of interest to an operator of the dashboard user interface 30. As noted above, in one exemplary application, the information obtained from the operational environment 16 comprises performance information relating to predefined Key Performance Indicators (KPIs). Under this arrangement, the KPIs are stored in a KPI data store 38. The KPI data store 38 is provided as part of the dashboard data stores 26 as illustrated. However, the KPI data store 38 may be located in any convenient physical or logical location that is accessible by the information management module 24. Referring to FIG. 2, system 10 is the same as that described with reference to FIG. 1. However, the performance bookmark data store 20 is alternatively illustrated as being stored within or as part of the dashboard data store 26, e.g., logically or physically stored as part of the same relational database, data store or other data storage structure used to maintain the KPI database or as a separate logical data structure within the dashboard data store 26.

Referring to FIGS. 1 and 2 generally, KPIs are meaningful indicators of performance relative to expectations. KPIs are sometimes provided in the form of targets and thresholds, and comprise measurable, definable metrics used to signify information of interest to an operator of the system 10. As a few examples, KPIs may comprise total customers, average sale per customer, total sales by region, productivity of employees, etc. KPIs are also often tied to strategies, goals or other objectives and require careful design and implementation in order yield intended results. As such, KPIs may not remain static but may be modified, added, deleted, etc. Moreover, KPIs may be provided in a number of different forms, such as targets or thresholds. An exemplary target may comprise a number of newly added customers. An exemplary threshold may comprise revenue growth rate, which may be characterized by a threshold consisting of a singular value or range of values.

Although some KPIs may be characterized by historical information, e.g., trends in sales, growth of income by year, number of products shipped by month, etc., in general, KPIs are biased toward real-time data. As such, the information management module 24 computes point-in-time actual values of KPIs and updates the determined values for the predefined KPIs, which are provided to the dashboard user interface 30 in real time or near real-time as the underlying data from the operational environment 16 changes. Accordingly, the KPI data store 38 maintains a times series of KPI values.

The KPIs may be derived from any combination of data available from the operational environment 16. The particular data required from the operational environment 16 to compute a current value for a given KPI will thus depend upon the definition of that KPI. Moreover, KPIs may be dependent or otherwise relate to or cross-reference one another. For example, a KPI that defines profit by year may relate to (or otherwise be derived from) a profit by month KPI for each of twelve consecutive months and a corresponding expense KPI for each of the twelve consecutive months.

The information from the KPI data store 38 is retrieved by the portal 28 and is coupled to the dashboard user interface 30 in an appropriate manner, such as may be dictated by the selected visual metaphor utilized to visualize the underlying data. The portal 28 may be implemented by any suitable means for conveying information from the dashboard data stores 26 to the dashboard user interface 30. For example, the portal 28 may comprise a service, agent, a network based applications server, web server etc.

The dashboard user interface 30 is a customizable visualization tool that associates at least one KPI with visual indicia. The visualization may comprise graphs, charts, lists, tables, alarms, and other visual aids to analyze and interpret the displayed KPIs. As the KPI values change over time, the view in the dashboard user interface 30 is updated to reflect the appropriate changes. The available KPIs can be filtered, sorted and displayed in any appropriate manner. Accordingly, the dashboard data stores 26 may further comprise a dashboard configuration data store 40 that stores various configurations, views and other information that defines the visual presentation of the KPI information.

The bookmark system 12 provides a mechanism to capture the state of the business performance as viewed through the dashboard user interface 30 for a particular point in time, and to retain that state of the data at that time for advanced monitoring and analysis. As such, the bookmark system 12 enables an operator the capability to capture, index, retrieve and use “performance bookmarks” of business performance information as measured at a previous point in time by the dashboard system 10.

Performance bookmarks are instances and relationships, and are not limited to snap shots captured of a static visual image of a dashboard screen from the dashboard user interface 30. As such, a retrieved dashboard view of a performance bookmark that is recalled from the bookmark system 12 is live and supports user interaction. The recalled performance bookmark may also allow subsequent filtering of displayed content, and/or the ability to separate the specific presentation mechanism from the saved state, allowing subsequent viewing to be performed through a variety of mechanisms and devices.

The bookmark management module 18 communicates with the information management module 24 and other system components to obtain the necessary information to create and construct a performance bookmark, which will be described in greater detail herein. The obtained information is written to the bookmark data store 20 when a performance bookmark is created. The bookmark management module 18 further communicates with the portal 28, e.g., so that stored instances of performance bookmarks can be reconstructed and displayed on the dashboard user interface 30. The bookmark interface 22 is a module that provides tools, e.g., within the dashboard user interface 30, that can be utilized by an operator so as to trigger and control the creation, recall and other manipulations (including interactive and administrative manipulations) of performance bookmarks.

Value may be derived in certain situations by the combination of multiple performance bookmarks over time, which are utilized to replay the state of the business across time, and to compare performance trends in a broader context than what would otherwise be available with a single KPI. Accordingly, the bookmark interface 22 may allow the operator to interact with the view defined by the recalled instance of the performance bookmark, e.g., to drill down on KPI values, and/or to replay the dashboard in time, which may cross one or more instances of performance bookmarks.

As noted in FIG. 1, the dashboard user interface 30 may provide feedback to the operational environment 16, e.g., to implement a decided-upon action based on an analysis of KPI information displayed on the dashboard user interface 30. For example, an action may be performed by a human or system component, typically in the context of managing or improving performance. An action may comprise for example, locating a new supplier, suspending a business process, redistributing available stock or other resources, etc. As such, a performance bookmark saved in the bookmark data store 20 may maintain actions and/or corresponding decisions that were taken in addition to appropriate point-in-time values for subsequent use in auditing the business actions. Thus, the performance bookmarks may also be utilized to evaluate actions taken for accountability purposes as will be described in greater detail herein.

Referring to FIG. 3, an exemplary data structure for a bookmark 50 is illustrated. The bookmark 50 includes a bookmark data page 52, which comprises attributes such as a name field and a timestamp. The name field identifies the bookmark 50 and may be entered by an operator, e.g., by using an appropriate data entry box provided by the bookmark interface 22 within the dashboard user interface 30. Alternatively, a name may be automatically generated and entered into the name field by a process, service or other component of the system 10, or the name field may be filled in with a name by a combination of automatic generation and operator entry.

The timestamp can take any suitable form and identifies a suitable reference in time to the creation of a particular instance of a bookmark 50. The time stamp may also be utilized to identify relevant information associated with the bookmark 50, e.g., by identifying the constituent components of the dashboard view and corresponding data associated with the particular instance of a bookmark based upon the information contained within, linked to or otherwise identified by the data structure of the bookmark 50. The data page 52 may also contain attributes such as a description field or other suitable fields to store relevant information that may be used for locating, retrieving, organizing or otherwise manipulating previously saved bookmarks 50. The data page 52 may also comprise a Role/ID attribute, which characterizes the role of the dashboard.

For example, the bookmark interface 22 (shown in FIGS. 1 and 2) may include a search tool that allows an operator to locate performance bookmarks of interest, e.g., by searching based upon criteria such as name, description, timestamp, role/ID or other uniquely identifying characteristics. Moreover, the bookmark interface 22 may include administrative functions, e.g., to organize, edit, add, sort, arrange and/or delete instances of bookmarks 50.

As noted in greater detail above, the operator of the dashboard system 10 may implement actions that affect business processes. This is schematically represented in FIG. 1, for example, by the communication of the dashboard user interface 30 with the operational environment 16. Correspondingly, the bookmark data structure, e.g., the data page 52 may associate with a record of actions 54, which can correspond to action(s), results, events and other characterizations of operator interaction with the dashboard user interface 30 that results in business action.

The bookmark 50 is further associated with a dashboard visual properties page 56. As noted in greater detail herein, each bookmark 50 is associated with the state of a dashboard view on the dashboard user interface 30, e.g., as of the time that the bookmark 50 is created or edited. Accordingly, the dashboard visual properties page 56 may be further conceptualized as having a dashboard page 58 and corresponding dashboard components page 60. The dashboard visual properties 56 (including the optional dashboard page 58 and corresponding dashboard components 60) may be stored as part of the bookmark store 20, the dashboard configuration store 40 or some other suitable storage arrangement.

According to an aspect of the present invention, a visual image of a dashboard screen is captured from the dashboard user interface 30, e.g., to a file or as an animated screen movie such as a flash animation or AVI file format, which may be saved, for example, in the dashboard configuration data store 26, within the bookmark data store 20 or within any other suitable storage location which is accessible to the system to capture the dashboard layout at the time that a performance bookmark is created.

At a technical implementation level, the dashboard user interface 30 may be compared to the granularity of a web page. The dashboard components 60 are constituent elements of the corresponding dashboard page 58 that displays a discrete set of information, answering a specific business question or supporting specific types of actions. These dashboard components 60 may interact and share information to implement the specific visual metaphor. Additional suitable information may be stored with the visual properties, e.g., a corresponding time stamp, etc.

The bookmark 50 further comprises information that associates KPIs 62 corresponding to the view of the dashboard user interface 30. Optionally, the performance bookmark may also associate related KPIs 64 to corresponding KPIs 62, which allows, for example, drill down and other interactive features of the corresponding bookmark 50. To support drill down, the system 10 must determine what KPI values must be retained in order to support drill-down. One exemplary approach utilizes a reachability graph. Under this arrangement, the depth of the drill-down state to be captured may be a configurable parameter of the graph.

Referring to FIG. 4, a chart 100 illustrates some exemplary triggering events that establish a condition 102 which may be utilized to trigger the creation of a performance bookmark 50. For example, an operator can manually create a performance bookmark at 104, such as by using the bookmark interface 22. Thus, the bookmark interface 22 defines a module that can detect a triggering event, such as an operator selecting a suitable menu option, selecting a button, box or other icon to cause an instance of a performance bookmark 50 to be created. A system service or other module, e.g., the bookmark management module 18, the information management module 24 or other component of the system 10 may detect a condition under which a performance bookmark 50 should be created. Once detected, the bookmark management module 18 may automatically create and store a performance bookmark at 106. As an alternative, the operator may be prompted, e.g., via the bookmark interface 22, as to whether a bookmark 50 should be created.

As an example, the system 10 may include a system service, e.g., provided as a component of either the bookmark management module 18 or the information management module 24, that automatically creates performance bookmarks when predetermined business situations are detected. The system 10 may then alert a human operator to the situation, and provide a reference to the created bookmark. Under this approach, the operator can retrieve the created performance bookmark and understand the specific context of the environment at the time that the situation was detected.

As noted in greater detail herein, a bookmark 50 may also be created when the system detects that an action has been taken, e.g., as a result of interaction with the dashboard at 108. Under this arrangement, the action may be associated with the performance bookmark as set out in greater detail herein. Performance bookmarks may also be continuously captured, such as at 110, or periodically captured at 112, such as by capturing a performance bookmark every predetermined time period.

Once a bookmark 50 has been established, a large number of capabilities become available to the operator. For example, a bookmark 50 may be retrieved, e.g., using the bookmark interface 22. Once retrieved and loaded into the dashboard user interface 30, an operator may interact with data from the past, e.g., perform drill-downs on KPI values, e.g., in the context of the historical snapshot, including the point in time KPI thresholds and targets. As another example, performance bookmarks 50 may be published. Once published, multiple parties can see point in time KPI values and interact with the dashboard view that is captured as part of the bookmark 50 to facilitate collaborative decision making.

In addition to locating and replaying historical KPI information, the bookmark interface 22 may allow a user to perform filtering functions, e.g., by selecting which KPIs to view in the bookmarked dashboard view, and/or to rewind, pause, and replay the dashboard view, which may span across multiple bookmarks. Still further, the system may be capable of showing trends, such as by showing trends of KPI values between instances of performance bookmarks 50.

As another example, an operator may set a bookmark 50 so as to preserve business information for audit, reconciliation and other purposes where a given bookmark 50 includes data associated with a business action. In one illustrative example, if a decision is made as a result of viewing a dashboard, the state of the KPIs that were used to base the action may be recorded and associated with the decision, such as by setting a bookmark 50 and by setting the corresponding action data in the action field 54. When an action is taken in the context of the dashboard, the system 10 may also be able to automatically (or manually) set a bookmark 50 and associate the action with the bookmark 50.

Referring to FIG. 5, a screen shot 200 of an exemplary dashboard user interface 30 is illustrated. As shown, the bookmark interface 22 consists of a transport bar 202 located towards the bottom of the screen. The transport bar 202 provides buttons, sliders and other objects that allow an operator to navigate through instances of performance bookmarks, such as by fast forwarding, rewinding, playing, pausing etc. Referring to FIG. 6, a screenshot 210 illustrates another exemplary dashboard user interface 30. As shown, an action has been taken at 212 by selecting a Modify Routing Rule option, which is captured and stored as part of a performance bookmark.

The system 10 may also include administrative capabilities, such as may be required to manage and organize created performance bookmarks.

The present invention may be practiced on any form of computer system, including a stand alone computer or one or more processors participating on a distributed network of computers. Thus, computer systems programmed with instructions embodying the methods disclosed herein, or computer systems programmed to perform various aspects of the present invention and storage or storing media that store computer readable instructions for converting a general purpose computer into a system based upon the various aspects of the present invention disclosed herein, are also considered to be within the scope of the present invention. Once a computer is programmed to implement the various aspects of the present invention, including the methods of use as set out herein, such computer in effect, becomes a special purpose computer particular to the methods and program structures of this invention. The techniques necessary for this are well known to those skilled in the art of computer systems.

Other computer system configurations can also be employed to perform the method of this invention, and to the extent that a particular system configuration is capable of performing the method of this invention, it is equivalent to the representative computer system and within the scope of this invention.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

The description of the present invention has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the invention. The embodiment was chosen and described in order to best explain the principles of the invention and the practical application, and to enable others of ordinary skill in the art to understand the invention for various embodiments with various modifications as are suited to the particular use contemplated.

Having thus described the invention of the present application in detail and by reference to embodiments thereof, it will be apparent that modifications and variations are possible without departing from the scope of the invention defined in the appended claims. 

1. A method of bookmarking a dashboard view in a dashboard system comprising: creating a performance bookmark comprising: assigning a name to said performance bookmark; providing a timestamp to said performance bookmark; storing said name and said timestamp in a bookmark data store; storing visual properties of said dashboard system at the time said performance bookmark is created; and storing relationships of information displayed by said dashboard view at the time said performance bookmark is created; and allowing an operator of said dashboard to recall previously created performance bookmarks, wherein recalling a select performance bookmark configures said dashboard to correspond with said visual properties and relationships of information recorded at the time said select performance bookmark was created.
 2. The method according to claim 1, wherein said creating a performance bookmark occurs upon detecting a triggering event.
 3. The method according to claim 2, wherein said detecting a triggering event comprises at least one of: detecting an operator-initiated request to create said performance bookmark; continuously and automatically creating and storing performance bookmarks; and periodically and automatically creating and storing performance bookmarks.
 4. The method according to claim 2, wherein said detecting a triggering event comprises: detecting a predetermined action performed as a result of an analysis of said dashboard view; automatically creating and storing said performance bookmark upon detecting the occurrence of said predetermined action; and associating said predetermined action with said performance bookmark.
 5. The method according to claim 2, wherein said detecting a triggering event comprises: detecting a business situation based upon data associated with a system service; automatically creating and storing an associated performance bookmark; alerting an operator to said business situation; and identifying said associated performance bookmark to said operator.
 6. The method according to claim 1, wherein said storing visual properties of said dashboard at the time said performance bookmark is created comprises: storing said dashboard page, each dashboard component, and a dashboard timestamp corresponding to the time an associated performance bookmark is created.
 7. The method according to claim 1, wherein said storing relationships of information displayed by said dashboard at the time said performance bookmark is created further comprises: storing additional data related to said data displayed in said dashboard that is necessary to allow drilling down of said data displayed in said dashboard.
 8. The method according to claim 1, further comprising allowing an operator of said dashboard to publish previously saved performance bookmarks.
 9. The method according to claim 1, further comprising allowing an operator to filter data displayed in a recalled performance bookmark of said dashboard.
 10. The method according to claim 1, further comprising providing bookmark navigational tools that allow an operator to rewind, pause and replay data displayed in a recalled performance bookmark of said dashboard.
 11. The method according to claim 1, further comprising providing a view of trends of predetermined dashboard data between instances of performance bookmarks.
 12. A system to bookmark a dashboard view in a dashboard system comprising: a module to create a performance bookmark that assigns a name to said performance bookmark, provides a timestamp to said performance bookmark, stores said name and said timestamp in a bookmark data store, stores visual properties of said dashboard system at the time said performance bookmark is created and stores relationships of information displayed by said dashboard view at the time said performance bookmark is created; and a module to allow an operator of said system to recall previously created performance bookmarks, wherein recalling a select performance bookmark configures said dashboard to correspond with said visual properties and relationships of information recorded at the time said select performance bookmark was created.
 13. The system according to claim 12, further comprising a module to detect a triggering event to cause an instance of a performance bookmark associated with said dashboard system to be created and stored.
 14. The system according to claim 13, wherein said module to detect a triggering event to cause an instance of a performance bookmark associated with said dashboard system to be created and stored comprises at least one of: a module to detect an operator initiated request to create a performance bookmark; a module to continuously and automatically create and storing said performance bookmarks; and a module to periodically and automatically create and storing said performance bookmarks.
 15. The system according to claim 13, wherein said module to detect a triggering event to cause an instance of a performance bookmark associated with said dashboard system to be created and stored comprises: a module to detect a predetermined action performed as a result of an analysis of said dashboard view; a module to automatically create and store a performance bookmark upon detecting the occurrence of said predetermined action; and a module to associate said predetermined action with said performance bookmark.
 16. The system according to claim 13, wherein said module to detect a triggering event to cause an instance of a performance bookmark associated with said dashboard system to be created and stored comprises: a module to detect a business situation based upon data associated with a system service; a module to automatically create and store an associated performance bookmark; a module to alert an operator to said business situation; and a module to identify said associated performance bookmark to said operator.
 17. The system according to claim 12, wherein said module to store visual properties of said dashboard at the time said performance bookmark is created comprises: a module to store said dashboard page, each dashboard component, and a dashboard timestamp corresponding to the time an associated performance bookmark is created.
 18. The system according to claim 12, wherein said module to store relationships of information displayed by said dashboard at the time said performance bookmark is created further comprises: a module to store additional data related to said data displayed in said dashboard that is necessary to allow drilling down of said data displayed in said dashboard.
 19. The system according to claim 12, further comprising a module to allow an operator of said dashboard to publish previously saved performance bookmarks.
 20. The system according to claim 12, further comprising a module to allow an operator to filter data displayed in a recalled performance bookmark of said dashboard.
 21. The system according to claim 12, further comprising a module to provide bookmark navigational tools that allow an operator to rewind, pause and replay data displayed in a recalled performance bookmark of said dashboard.
 22. The system according to claim 12, further comprising a module to provide a view of trends of predetermined dashboard data between instances of performance bookmarks.
 23. A computer program product to bookmark a dashboard view in a dashboard system comprising: a computer usable medium having computer usable program code embodied therewith, the computer usable program code comprising: computer usable program code configured to create a performance bookmark that assigns a name to said performance bookmark, provides a timestamp to said performance bookmark, stores said name and said timestamp in a bookmark data store, stores visual properties of said dashboard computer program product at the time said performance bookmark is created and stores relationships of information displayed by said dashboard at the time said performance bookmark is created; and a computer usable program code configured to allow an operator of said dashboard to recall previously created performance bookmarks, wherein recalling a select performance bookmark configures said dashboard to correspond with said visual properties and relationships of information recorded at the time said select performance bookmark was created.
 24. The computer program product according to claim 23, further comprising a computer usable program code configured to detect a triggering event to cause an instance of a performance bookmark associated with said computer program product to be created and stored.
 25. The computer program product according to claim 24, wherein said computer usable program code configured to detect a triggering event to cause an instance of a performance bookmark associated with said computer program product to be created and stored comprises at least one of: a computer usable program code configured to detect an operator initiated request to create a performance bookmark; a computer usable program code configured to continuously and automatically create and storing said performance bookmarks; and a computer usable program code configured to periodically and automatically create and storing said performance bookmarks.
 26. The computer program product according to claim 24, wherein said computer usable program code configured to detect a triggering event to cause an instance of a performance bookmark associated with said computer program product to be created and stored comprises: a computer usable program code configured to detect a predetermined action performed as a result of an analysis of said dashboard view; a computer usable program code configured to automatically create and store a performance bookmark upon detecting the occurrence of said predetermined action; and a computer usable program code configured to associate said predetermined action with said performance bookmark.
 27. The computer program product according to claim 24, wherein said computer usable program code configured to detect a triggering event to cause an instance of a performance bookmark associated with said computer program product to be created and stored comprises: a computer usable program code configured to detect a business situation based upon data associated with a computer program product service; a computer usable program code configured to automatically create and store an associated performance bookmark; a computer usable program code configured to alert an operator to said business situation; and a computer usable program code configured to identify said associated performance bookmark to said operator.
 28. The computer program product according to claim 23, wherein said computer usable program code configured to store visual properties of said dashboard at the time said performance bookmark is created comprises: a computer usable program code configured to store said dashboard page, each dashboard component, and a dashboard timestamp corresponding to the time an associated performance bookmark is created.
 29. The computer program product according to claim 23, wherein said computer usable program code configured to store relationships of information displayed by said dashboard at the time said performance bookmark is created further comprises: a computer usable program code configured to store additional data related to said data displayed in said dashboard that is necessary to allow drilling down of said data displayed in said dashboard.
 30. The computer program product according to claim 23, further comprising a computer usable program code configured to allow an operator of said dashboard to publish previously saved performance bookmarks.
 31. The computer program product according to claim 23, further comprising a computer usable program code configured to allow an operator to filter data displayed in a recalled performance bookmark of said dashboard.
 32. The computer program product according to claim 23, further comprising a computer usable program code configured to provide bookmark navigational tools that allow an operator to rewind, pause and replay data displayed in a recalled performance bookmark of said dashboard.
 33. The computer program product according to claim 23, further comprising a computer usable program code configured to provide a view of trends of predetermined dashboard data between instances of performance bookmarks. 